You are here: Reference > Known Issues

Known Issues

Component: Customized Diagrams

Issue: Upgraded source 7.2.2 system has far too many customized Diagrams

Cause: When IONE 6.0.1 was upgraded to PME 7.2.2, the diagrams were copied to the new system. When Configuration Manager reads the 7.2.2 system, Configuration Manager considers these diagrams as being customized.

Solution: No action required.

Component: Customized Diagrams

Issue: Configuration Manager does not copy a file on Write to System.

Cause: PME 8.2 ships with _iEM3150_3250.bmp and _iEM3155_3255.bmp. If either of these files are in a saved archive, Configuration Manager does not consider them to be modified files because it compares the file content, not the dates.

Solution: Ignore the diagrams. If you do not want the diagrams to display in the Configuration Manager Content grid, or do not want to take up disk space in the archive or on the target system:

  • Delete the diagrams (or remove them from the PME folder structure) on the source system before using Configuration Manager.
  • Delete the diagrams on the target system after the Write to System completes.

Component: Database archive information

Issue: Configuration Manager displays an incorrect archive size and start date.

Solution: Verify the database size in Windows Explorer. The default database archive location is ...\Power Monitoring Expert\Database\Archive.

Component: Hierarchy

Issue: Hierarchy is overwritten by reconfigure system.

Configuration Manager extracts the source system hierarchy template (.xml file) and saves a copy to the CM Migration Files folder on the target. Import this hierarchy XML file on the target as described in the guide.

Solution: To manually recreate the source hierarchy on the target PME 8.2 system, see StruxureWare™ Power Monitoring Expert 8.0 Hierarchy Configuration Guide.

Component: Hierarchy

Issue: Hierarchy nodes with apportionment are wrong.

Cause: A Spanish source system using one locale was copied to a Spanish system using a different locale.

Solution: Configuration Manager supports Spanish systems using the same locale only.

See When to use the tool for information on the power monitoring systems Configuration Manager supports.

Component: Historical Devices

Issue: Query Server and VIPs display as historical devices after write to system

Cause: There is no way to know which sources are actual devices or software nodes as both as classified as "physical" sources.

Solution: Complete the manual configuration steps and start the services. Once the services start the Query Server and VIPs will no longer appear as historical devices.

Component: PQDIF Exporter

Issue: PQDIF Exporter using the source server name on the target system

Cause: The SQL Server instance for the PQDIF Exporter combines the server name and the database instance name. Since Configuration Manager does not know the database instance name on the target, it keeps the source name.

Solution: Manually update the PQDIF Exporter SQL Server instance using the target server name and database instance name.

See Supporting Guides for more information.

Component: Logical Device Types / Managed Circuit Types

Issue: After writing an IONE 6.0.1 source archive to a new PME 8.2 system, 11 new logical device types / managed circuit types appear on the target PME 8.2 system.

Cause: The Database Manager scripts include these device types by default.

Solution: No action required. You can ignore the 11 new logical device types / managed circuit types.

Component: Topic Equivalencies

Issue: Customized Smart Measurements do not get copied to the target system

Cause: The database upgrade scripts overwrite customized Smart Measurement values.

Solution: Manually recreate Smart Measurements on the new system. Smart measurements are stored in the Configuration.Configuration... tables in the Application Modules database.

Component: Vista Diagrams

Issue: After upgrading a source archive to a new PME 8.2 system, customized Vista diagrams do not display when Open Diagram for Meter option is selected.

Cause: Newer versions of default Vista diagrams on the target system open by default.

Solution: Manually recreate the customized DMG files or change the link type in the parent diagram to Open User Diagram, and then link to the customized DMG file.